Open
Conversation
Update master from jamesfer
Query can now return objects as result feat: Typings for builder and query methods
Author
|
@jamesfer is this something that is interesting for the project? Just let me know some of your thoughts |
feat(builder): Return type hint for return object
Bastianowicz prepare script
Bastianowicz
force-pushed
the
query_typing_squashed
branch
from
a04eccb to
92b3a96
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
I introduced a returnObject-Method to allow the following statement:
RETURN { foo: bar }and an optional generic G which represents the graphmodel of the cypher (the nodes and relations that are accessable in the methods).This prevents you from comparing or using non-existent properties, nodes or relations.
99% of the changes are compatible with former versions and the new generics are all optional.